sudo service mobicents-load-balancer ( start | stop | status | restart | help )
This appliance is ready to be used out of the box. The user is ec2-user and
has a full sudo access (no password required). The logs are available in the le
/server/mobicents-load-balancer/console.log. You can manage Mobicents Load Balancer
by using the following command:
sudo service mobicents -load - balancer ( start | stop | status | restart | help )
This appliance is ready to be used out of the box. The user is ec2-user and has a full sudo access (no password required). The logs are available in the file /server/mobicents-load-balancer/console.log. You can manage Mobicents Load Balancer by using the following command:
sudo service mobicents-load-balancer ( start | stop | status | restart | help )
1. Launch a new instance of the Mobicents Sip Servlets appliance. The user is ec2-user and has a full sudo access (no password needed).
2. Set-up the IP of the load balancer. Open the file /etc/syscong/mobicents-sip-servlets and edit the MOBICENTS_LB_IP property.
sudo vi /etc/sysconfig/mobicents-sip-servlets
If you want to use an elastic IP for the SIP load load balancer, you can set the MOBICENTS_LB_ IP property to the following
MOBICENTS_LB_IP ='dig +short <public_dns>'
Where <public dns> is the public DNS of your elastic IP. For instance, if your elastic ip is 50.16.205.218, your public DNS will be something like ec2-50-16-205-218.compute-1.amazonaws.com.
3. Consider installing the use cases if you want to use them (Section 1.3.1), and jump to the step 6.
Otherwise, upload your applications to the container. From your computer:
scp -i <your_keyfile.pem> <your_application.war> ec2-user@<your_instance_ip>:/home/ec2-user
From your instance:
sudo mv /home/ec2-user/*.war /server/mobicents-sip-servlets/server/all/deploy
4. Edit the dar conguration le.
sudo vi /server/mobicents-sip-servlets/server/all/conf/dars/mobicents-dar.properties
5. Restart the Mobicents Sip Servlets container in order to apply the changes. (Don't forget it!)
sudo service mobicents-sip-servlets restart
6. Once you have customized your appliance, create a new image of this appliance in the Amazon EC2 console (See Figure 1.1). You can now start or stop as many instances of this new image as you wish.
You can manage Mobicents Sip Servlets by using the following command:
sudo service mobicents-sip-servlets ( start | stop | status | restart | help )
1. Register a new environment, containing your Mobicents Sip Servlets appliance created before (See Subsection 1.2.2, Step 6). First, copy this content to a file named mobicents-sip-servlets.yml and edit the cloud id to the id of your AMI. If you don't have a 64 bits image, just put the same id in both sections.
---
platforms :
- name : Mobicents Sip Servlets Platform
platform_versions :
- version_number : 1
images :
- name : Mobicents Sip Servlets
description : Mobicents Sip Servlets 1.5
uid : mss-1
can_scale_out : true
services :
- mobicents_sip_servlets
cloud_images :
- cloud : ec2
region : us-east-1
architecture : i386
cloud_id : <your_ami>
- cloud : ec2
region : us-east-1
architecture : x86_64
cloud_id : <your_ami>
2. Then, register this environment in SteamCannon.
cd /opt/steamcannon/ export RAILS_ENV=production export FILE=/root/mobicents-sip-servlets.yml /opt/jruby/bin/jruby -S rake app:platforms:load_from_yaml cd
If you want to remove a platform, you can reinitialize the database of SteamCannon:
cd /opt/steamcannon /etc/init.d/jboss-as stop /opt/jruby/bin/jruby -S rake db:drop:all ./bin/appliance_initialization.sh /etc/init.d/jboss-as start cd
1. Ensure that the port 8080 is open for all trac in the security group within which your SteamCannon instance is running.
2. By default, SteamCannon start new instances in a new security group called steamcannon. Ensure that all the TCP, UDP and ICMP trac is allowed between the steamcannon security group and the security group within your Mobicents Load Balancer is running (in both directions).
3. Open a web browser on http://<your instance's public ip>:8080 and register an account (Figure 1.2). Make sure to use Firefox when you use the web interface.
(A bug in SteamCannon prevent it from working in Safari.)
Figure 1.2: Register an account on SteamCannon.
4. Create a new environment of the platform you have created in the previous section (Figure 1.3). You can start and stop Mobicents Sip Servlets instances within this environment.
1. You need a working copy of Twiddle, with the same version than the one distributed with JBoss AS 5.1. The simplest way to get it is to get a fresh copy of Mobicents Sip Servlets.
yum install -y unzip wget http://sourceforge.net/projects/mobicents/files/Mobicents%20Sip%20Servlets/Mobicents%20Sip%20Servlets%201.5.0.FINAL/mss-1.5.0.FINAL-jboss-jdk6-5.1.0.GA-1012212016-LGPL.zip/download unzip mss-1.5.0.FINAL-jboss-jdk6-5.1.0.GA-1012212016-LGPL.zip sudo rm mss-1.5.0.FINAL-jboss-jdk6-5.1.0.GA-1012212016-LGPL.zip
2. Install the cloud monitor SteamCannon agent.
sudo yum install -y svn
Figure 1.3: Create an environment.
svn checkout https://mobicents.googlecode.com/svn/trunk/cloud/sip-servlets/scaler
3. (Optional.) Personalize the monitoring. Two les are worth checking. Those are cloud-monitor-sc-client/src/name/leruitte/cloud/monitor/client/Parameters.java and cloud-monitor-sc-client/src/name/leruitte/cloud/monitor/model/Threshold.java.
4. Build the Monitor SteamCannon agent executable.
sudo yum install -y java-1.6.0-openjdk-devel cd scaler/build/ ./build_jar.sh cd
5. Make sure an environment is running (Subsection 1.2.3).
6. Start the monitoring process.
cd scaler/exe/ ./scaler.sh -s localhost -u <your_steamcannon_user> -p <your_steamcannon_password>